home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
wildcat
/
camcrc20.zip
/
CAMS-CRC.DOC
< prev
next >
Wrap
Text File
|
1992-10-29
|
19KB
|
481 lines
CAMS-CRC Upload Processor for WildCat!
DISCLAIMER . . . . . . . . . . . . . . . . . . . . . . . . . 2
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . 3
FILES INCLUDED . . . . . . . . . . . . . . . . . . . . . . . . 3
CAMS-CRC.EXE. . . . . . . . . . . . . . . . . . . . . . . 3
OUTCOMM.EXE . . . . . . . . . . . . . . . . . . . . . . . 3
NOADD.TXT . . . . . . . . . . . . . . . . . . . . . . . . 3
SCANFILE.BAT . . . . . . . . . . . . . . . . . . . . . . 3
DLPATH.LST . . . . . . . . . . . . . . . . . . . . . . . 3
CAMS-CRC.TXT . . . . . . . . . . . . . . . . . . . . . . 3
FILE_ID.TXT . . . . . . . . . . . . . . . . . . . . . . . 3
GIF.TXT . . . . . . . . . . . . . . . . . . . . . . . . . 3
PKUNZIP.TXT . . . . . . . . . . . . . . . . . . . . . . . 3
STRIPZIP.TXT . . . . . . . . . . . . . . . . . . . . . . 3
VIRUS.TXT . . . . . . . . . . . . . . . . . . . . . . . . 3
REGISTER.DOC . . . . . . . . . . . . . . . . . . . . . . 3
CAMS-CRC.EXE Parameters. . . . . . . . . . . . . . . . . . . . 4
CAMS-CRC.EXE BUILD/UPLOAD . . . . . . . . . . . . . . . . 4
BUILD Parameter Options . . . . . . . . . . . . . . . . . 4
/DL:xxxx . . . . . . . . . . . . . . . . . . . . . . 4
/C:path. . . . . . . . . . . . . . . . . . . . . . . 4
/R:xx. . . . . . . . . . . . . . . . . . . . . . . . 4
UPLOAD Parameter Options. . . . . . . . . . . . . . . . . 4
/C:path. . . . . . . . . . . . . . . . . . . . . . . 4
/D . . . . . . . . . . . . . . . . . . . . . . . . . 5
/F:xxxx. . . . . . . . . . . . . . . . . . . . . . . 5
| /G . . . . . . . . . . . . . . . . . . . . . . . . . 5
/R:xx . . . . . . . . . . . . . . . . . . . . . . . 5
/SCAN . . . . . . . . . . . . . . . . . . . . . . . 5
/STZ . . . . . . . . . . . . . . . . . . . . . . . . 5
INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . 6
CAMS-CRC.EXE BUILD /R:80 /DL:filename . . . . . . . . . . 6
BADFILES.BAT. . . . . . . . . . . . . . . . . . . . . . . 6
DUPFILES.BAT. . . . . . . . . . . . . . . . . . . . . . . 6
CAMS-CRC.CFG . . . . . . . . . . . . . . . . . . . . . . 7
SCANFILE.BAT . . . . . . . . . . . . . . . . . . . . . . 8
DISCLAIMER
This software is provided without any guarantee, either expressed
or implied. All responsibilities for its use rest with the user
of the software and not the author.
Cams-CRC software and this document are (C) Copyright 1992 by
Cam DeBuck Software. All rights reserved World Wide.
LICENSE
Cams-CRC is not in the Public Domain. Cams-CRC is not free.
Non-registered users are granted a limited, 30-day license to
determine whether or not the program meets their needs.
Continued use of Cams-CRC beyond the 30-day evaluation time
period requires registration of the program. Use of non-
registered copies of Cams-CRC beyond the original evaluation
period is strictly prohibited.
No one may modify Cams-CRC for any reason, in any way, including
but not limited to decompiling-compiling, patching,
disassembling, or reverse engineering the program.
Cams-CRC may be copied and distributed to others, subject to the
above restrictions and the following:
* Cams-CRC must be copied in unmodified form, including the
file containing this license information.
* Complete Cams-CRC documentation must be included.
* No copying fee of any type may be assessed other than basic
charges for the cost of the copying medium.
* Cams-CRC may not be distributed with any other software or
hardware product(s) without the express written permission
of Cam DeBuck Software.
Sysops (bulletin board SYStem OPerators) may make Cams-CRC
available for downloading by their users as long as all above
conditions are met.
Commercial Distributors of Public Domain, ShareWare, or User-
Supported software may distribute Cams-CRC subject to the above
conditions only after obtaining specific written permission from
Cam DeBuck Software and filling out a registration form for
upgrade notifications. This condition supersedes any and all
previous agreements.
CAMS-CRC Upload Processor for WildCat 3.5
INTRODUCTION
Thank you for purchasing CAMS-CRC Upload Checker. You'll find this to be
a very FAST program when checking for .ZIP files. The processing of .GIF files
is a little slower due to the .GIF file format. CAMS-CRC checks for a VALID
.GIF file by uncompressing and displaying it in it's virtual screen (You cannot
see it, but the program does). This allows the program to test for a valid
.GIF file.
During the process of both the .ZIP and .GIF files, it gets a 32-bit CRC
of the file and then checks to see if it's in the DATABASE file. If it is,
then the file is rejected. A file called DUPS.LOG is always created and is
displayed to the caller after the entire file has been checked (According to
the paramters that you used). This file will tell the user what files were
duplicates and what percentage were duplicates. Also, various information
will be sent to the user as certain things are being done. This will let the
user know what you are doing and will keep the users attention (At least for
a little while).
FILES INCLUDED
You should have the following files on your DISK or .ZIP file:
CAMS-CRC.EXE - This is the heart of the program
OUTCOMM.EXE - This will display the various information out the
comport
NOADD.TXT - Your BBS ADD (Or N/A) telling where the file came from.
If you do not want to add a comment to the ZIP file,
leave this file containing a SPACE in it
SCANFILE.BAT - A sample SCANFILE.BAT file to use
DLPATH.LST - A sample download path file to use with the /DL:x switch
CAMS-CRC.CFG - This is a configuration file that needs to be placed in
each NODE directory. It contains some very important
information.
The following files are TEXT files that are displayed to the user
using OUTCOMM.EXE (Which is written by me). Feel free to modify any of
these files. You can use the WildCat Color codes if you wish:
CAMS-CRC.TXT - Text file explaining that the file is being checked
for duplicates.
FILE_ID.TXT - Text file explaining that the description file is being
extracted from the .ZIP file.
PKUNZIP.TXT - Text file explaining that the file is being extracted.
STRIPZIP.TXT - Text file explaining that you are removing comments
from the .ZIP file.
VIRUS.TXT - Text file explaining that you are checking for a virus.
GIF.TXT - Text file explaining that the integrity of the GIF is
being processed.
3
CAMS-CRC.EXE Parameters
CAMS-CRC.EXE has several paramters passed to it. There are currently
two different MODES available. They are: BUILD and UPLOAD
These paramters will be the FIRST parameters on the command line with
the optional parameters following (i.e.):
CAMS-CRC.EXE BUILD/UPLOAD [optional flags]
BUILD Parameter Options
The BUILD parameter is used to build or append to the DataBase any
files that you have collected (This could be from a CD-ROM, or just
from downloading files from another BBS. This file is a TEXT file. It will
search ALL files and directories within the current directory. So if you
specify just the I:\ drive by itself (In the TEXT file), the program will
search your entire I drive.
[Optional Flags or Paramters]
/DL:xxxx - Where xxxx represents the full path and name of your .LST
file. This paramter is REQUIRED.
/C:path - If you wish to specify where you want the *.CR? files created,
then you will need to specify the PATH of the database files.
This is an OPTIONAL paramter. The default is in the current
directory.
/R:xx - This is the Ratio to use for Duplicate ZIP files. The
default is set to 70 percent. Because some authors will only update
their EXE files or HISTORY files, it is necessary sometimes to
have this above 70. This is an OPTIONAL paramter.
UPLOAD Parameter Options
The UPLOAD parameter is used to test an INDIVIDUAL file from WildCat. This
may be a .ZIP or .GIF file. If anything else is specified, then nothing
will happen.
[Optional Flags or Paramters]
/C:path - If you wish to specify where the CAMS-CRC.CRC file is located,
then you will need to specify the PATH of the database files.
This is necessary when running a multi-node BBS.
This is an OPTIONAL paramter. The default is in the current
directory. If you're running a multi-node system, I suggest
that you use this paramter.
4
/D - Tells the program to add the Newest and Oldest Files in
description of the file. It also adds the total number of Files
within a ZIP. This paramter only works with .ZIP files. It works
only if a FILE_ID.DIZ file is found (Until WC changes something).
/F:xxxx - This is the full path and name of the file to test. If
you are using this via your SCANFILE.BAT file, then all
you need to do is use the %1 paramter (i.e., /F:%1 ).
This paramter is REQUIRED.
| /G - If processing a GIF file, this tells the program to add
| the screen resolution and the COLOR of the GIF to the DIR
| file. This only works .GIF files. It is an OPTIONAL parameter.
/R:xx - This is the Ratio to use for Duplicate ZIP files. The
default is set to 70 percent. This means that a user can
have up to 69 percent of dups before the file is rejected.
Because some authors will only update their EXE files or HISTORY
files, it is necessary sometimes to have this above 70.
I personally like using 50% ratio. This is an OPTIONAL paramter.
/SCAN - This tells the program to use SCAN.EXE to check for a virus.
Be sure you enable your SCANOPTIONS in the CAMS-CRC.CFG for
each node. This is an OPTIONAL paramter.
/STZ - This will remove any ZIP comments and place a ZIP comment of
your own. You will need to modify the NOADD.TXT file if you
want your own ZIP comment added. This is an OPTIONAL parameter.
5
INSTALLATION
First, you will need to create a directory. I suggest \CAMS-CRC. Unzip
the the CAMCRCxx.ZIP (Where xx is the version number) into this directory.
Second, you will need to create a TEXT file that has all the paths to your
files. Each path will need to be on a seperate line. If you have dedicated
a hard drive to just files, then make your life easier by simply defining the
Drive. An example file can look like this:
C:\FILES\WINDOWS
C:\FILES\GIFS
D:\
E:\
F:\
The above example could of been simplied for the first two paths by using
C:\FILES. Remember, that the program will check the current directory and
any directions within the current directory for .ZIP of .GIF files. The last
three paths will tell the program to search the entire hard drive for .ZIP or
.GIF files.
Depending on the number of .GIF files you have (And how fast your computer
is), this process may take a while. You will notice that .ZIP files will FLY
on by.
Once you have created your TEXT file, you will need to build your initial
database. This is very simple. Just do this:
CAMS-CRC.EXE BUILD /R:80 /DL:filename (Where filename is the name of the
text file you just created)
After the program has completed, you will find two BATCH files and a
DUPS.LOG. The DUPS.LOG contains information pertaining for each .ZIP
or .GIF file. Use this as a reference.
The BATCH files are called:
BADFILES.BAT - This contains any Bad Files that were found during the
initial build. Basically, these should be corrupted
files (.GIF or .ZIP). It is possible that your .ZIP
files will be good if they were compressed with an
earlier version of PKZip. This program requires that
all files be created using PKZip v1.10.
DUPFILES.BAT - These will contain the path to any Duplicate Files that
were found during the build process.
NOTE: These BATCH files contain a statement to DELETE these files. If
you want to remove these duplicates or bad files, simply type in
the name of the batch file and they will be removed. You will then
need to run WCFILE and remove the file descriptions.
6
CAMS-CRC.CFG File
You will need to make sure you create a CAMS-CRC.CFG file in each
NODE Directory. The CAMS-CRC.CFG contains 5 lines (Some of which are
optional). The order doesn't matter, but make sure everything is in CAPS:
WCFILEOPTIONS= : This is the options to use for WCFILE.EXE. Be sure
you use these command line options: /E /F /K
Do NOT use /A: as I automatically figure this
information out.
FILEAREADAT= : This is the PATH/NAME of your FILEAREA.DAT file. This
is used in conjunction with the WCFILEOTPIONS. It's
very important that you have this set correctly.
SCANOPTION= : This is the option(s) to use for SCAN.EXE. SCAN.EXE
is a Virus Scanning program McAfee Associates. See
the documentation on what options you want to set.
My example CAMS-CRC.CFG has some normal settings
which work very nicely.
WORKPATH= : This is the temporary WORK directory to use. Each
NODE needs to have its own WORK directory. If you
give two nodes the same directory, you will only
cause problems. Be sure you use a different
directory for each node. I suggest the WORK
directory be off of the ROOT directory.
OLDESTFILE : During an Upload Process, you can specify what the
oldest file in the archive can be (In the format of
MM/DD/YY). If one file is found, the entire upload
will fail. The DUPS.LOG (Which you should rename
during the upload process) will contain information
that the file failed because of being out of date.
7
INSTALLING SCANFILE.BAT
Installing the SCANFILE.BAT file is very simple. I suggest that you use our
example SCANFILE.BAT file and modify it to fit your needs. In most cases you
will find that you won't have to do anything to it.
When a file is uploaded (This can be done locally or remotely), the DUPS.LOG
file is created. It's very important that you delete this file after the
file has been processed. I suggest that you copy it to another file and purge
it when you feel it's necessary. You'll find that our example SCANFILE.BAT
file does this. A SCANFILE.BAT goes in each of your NODE Directories.
Here is a sample SCANFILE.BAT file:
echo off
echo Delete the SCANFILE.BAD file (Just in case it might exist)
IF EXIST SCANFILE.BAD DEL SCANFILE.BAD
echo Now let's do the REAL WORK
CAMS-CRC UPLOAD /C:C:\CAMS-CRC /F:%1 /D /R:50 /SCAN
echo Display the DUPS.LOG file so the user can see what percentage of dups.
OUTCOMM.EXE DUPS.LOG
echo Copy the DUPS.LOG to a permanent file
echo This is NOT necessary, but it keeps a RUNNING log of everything.
copy C:\CAMS-CRC\ALL-DUPS.LOG+DUPS.LOG ALL-DUPS.LOG
echo Delete the DUPS.LOG file
del DUPS.LOG
IF EXIST WCFILE.LOG DEL WCFILE.LOG
Additional Information
You will notice a "|" character at the beginning of a new line. This
indicates that this feature has been removed due to the way WildCat! works.
If WildCat! would create a DESCRIPT file (Which would tell the program what
type of description the user entered via the BBS), I could then add some
additional information. OR if WildCat would add an option to the WCFILE.EXE
to generate a TEXT file of the description, I could then enable the option.
Please ask Mustang Software, Inc. to add such a feature!
When WCFILE.EXE is excuted, it will SOMETIMES leave behind a WCFILE.LOG. I
have no idea why it is doing this, but I suggest that you add to your
SCANFILE.BAT an "IF EXIST WCFILE.LOG DEL WCFILE.LOG". Also, when WCFILE.EXE
runs, it might generate a WCFILE.ERR. This should NOT be deleted until the
Sysop checks it out.
If you have any problems, please contact me at:
BBS (801)489-3558 [HST 1440]
VOICE (801)489-4878 [M-F 9 to 5, Sat 9 to 12]
Order using: Visa, MasterCard, Discover, Diners Club or JCB Cards,
Please call: ORDERS ONLY 1-800-392-8892 [M-F 9 to 5, Sat 9 to 12]
8